- I recommend the Pixel 9 to most people looking to upgrade - especially while it's $250 off
- Google's viral research assistant just got its own app - here's how it can help you
- Sony will give you a free 55-inch 4K TV right now - but this is the last day to qualify
- I've used virtually every Linux distro, but this one has a fresh perspective
- The 7 gadgets I never travel without (and why they make such a big difference)
Project drift: How to deal with IT’s silent project killer

Always renegotiate
Renegotiating project timelines and deliverables goes hand in hand with having that early meeting with stakeholders about project enhancements, because taking on significant new enhancements will lengthen project timelines and will contribute to budget overruns.
Business managers know this, but they also want to get as much functionality from a project as they can. What they do then is have their staff “trial run” a project and provide feedback like, “This is nice, but I’d really like to see this, too,” or, “No, we can’t use this. We need to also build an interface to system XYZ.”
These requests often come when IT is expecting feedback primarily on minor system bugs that need to be resolved, but business users don’t always see it that way. Instead, they view QA as a “systems acceptance” test — i.e., will they accept the project as is, or is it insufficient for their needs?